Review the following restrictions, limitations, and behavioral characteristics for Fabric Attach.
IS-IS and FA must be globally enabled on the FA Server, for FA to operate successfully.
Static MAC, Static ARP and configuration of a static IGMP group are not supported on FA-enabled ports.
An FA port cannot be a BROUTER port.
You cannot enable FA on an existing Transparent Port UNI or a C-VLAN UNI port.
FA I-SID-to-VLAN assignment mapping requests from a client or proxy device can be accepted or rejected by the FA Server.
On an FA-enabled port or MLT, you must first disable LACP before you change the LACP key.
You can only enable VLACP on an FA enabled MLT; VLACP is not supported on FA enabled non-MLT ports.
On VLACP enabled ports, FA and LLDP signaling run independent of the VLACP state. Therefore, requests and responses are exchanged between the FA Server and client or proxy devices even if VLACP is operationally down. However, forwarding of data traffic is dependent on VLACP being operationally up on the port.
For example, if VLACP is enabled on the FA Server side of the link but not on the proxy or the client side, the FA Server learns the I-SID-to-VLAN assignment mappings and creates the required I-SIDs on its device. However, data traffic is not forwarded on the port until VLACP is operationally up.
FA uses the virtual MAC to create the FA system ID when the FA is on an SMLT. If you delete the SPBM instance, then this information is no longer available. Therefore, you must delete the FA on SMLT before deleting the SPBM instance.
You cannot enable FA and Endpoint Tracking simultaneously on the same interface.